Systems and methods for estimating time of arrival for vehicle navigation

ABSTRACT

Systems and methods for estimating time of arrival for vehicle navigation are described. One embodiment of a method includes determining a route for a vehicle to reach a destination from a current location determining, by the computing device, an estimated time for reaching the destination from the current location. Embodiments of the method additionally include determining, by the computing device, a current range of the vehicle, based on current fuel level and vehicle fuel efficiency and determining, by the computing device and based on the current range, whether the vehicle can reach the destination without refueling. Some embodiments include revising, by the computing device, the estimated time for reaching the destination to include a waypoint to refuel in response to determining that the vehicle cannot reach the destination without refueling and providing, by the computing device, the estimated time for reaching the destination for display to a user.

TECHNICAL FIELD

Embodiments described herein generally relate to systems and methods forestimating time of arrival for vehicle navigation and, specifically, todetermining way-points and predicting times for stopping at theway-points in time of arrival calculations.

BACKGROUND

Many current vehicles are equipped with a navigation system to calculatean estimated time of arrival (ETA) to a destination. However, oftentimesthis estimation does not take into account stops that the user may makealong the route. While these navigation systems are helpful, they oftenunderestimate and are otherwise inaccurate in predicting the time itwill take to reach the destination.

Accordingly, a need exists for alternative vehicle routing and/orestimating time to a destination.

SUMMARY

Systems and methods for estimating time of arrival for vehiclenavigation are described. One embodiment of a method includesdetermining, by a computing device, a route for a vehicle to reach adestination from a current location determining, by the computingdevice, an estimated time for reaching the destination from the currentlocation. Embodiments of the method additionally include determining, bythe computing device, a current range of the vehicle based on currentfuel level and vehicle fuel efficiency and determining, by the computingdevice and based on the current range, whether the vehicle can reach thedestination without refueling. Some embodiments include revising, by thecomputing device, the estimated time for reaching the destination toinclude a waypoint to refuel in response to determining that the vehiclecannot reach the destination without refueling and providing, by thecomputing device, the estimated time for reaching the destination fordisplay to a user.

In another embodiment, a system includes an odometer for determiningdistances traveled by the vehicle, a fuel gauge for determining acurrent fuel level of the vehicle, and a computing device. The computingdevice stores logic that, when executed by a processor, causes thecomputing device to determine a distance for reaching a destination froma current location, determine a current range of the vehicle, based onthe current fuel level and a vehicle fuel efficiency, and determinebased on the current range, whether the vehicle can reach thedestination without refueling. Additionally, in response to determiningthat the vehicle cannot reach the destination without refueling, thelogic may cause the computing device to determine an estimated time forreaching the destination, wherein the estimated time for reaching thedestination includes travel time to waypoint to refuel and a predictedrefueling time. The logic may cause the computing device to provide theestimated time for reaching the destination for display to a user.

In yet another embodiment, a system includes a vehicle and a computingdevice. The computing device stores logic that, when executed by aprocessor, causes the computing device to determine an estimated timefor reaching a destination from a current location, predict whether awaypoint will be taken before reaching the destination, and in responseto determining that the vehicle will take the waypoint before reachingthe destination, revise the estimated time for reaching the destinationto include the waypoint. The logic may additionally cause the computingdevice to provide the estimated time for reaching the destination fordisplay to a user.

These and additional features provided by the embodiments of the presentdisclosure will be more fully understood in view of the followingdetailed description, in conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments set forth in the drawings are illustrative and exemplaryin nature and not intended to limit the disclosure. The followingdetailed description of the illustrative embodiments can be understoodwhen read in conjunction with the following drawings, where likestructure is indicated with like reference numerals and in which:

FIG. 1 depicts a vehicle interior according to embodiments disclosedherein;

FIG. 2 depicts a user interface for selecting a destination that may beprovided by a vehicle computing device, according to embodimentsdisclosed herein;

FIG. 3 depicts a user interface for viewing a route that may be plannedby a vehicle computing device, according to embodiments disclosedherein;

FIG. 4 depicts a user interface for providing one or more optionsrelated to calculating a time of arrival to a destination, according toembodiments disclosed herein;

FIG. 5 depicts a user interface for calculating a time of arrival to adestination, while factoring in one or more waypoint stops, according toembodiments disclosed herein;

FIG. 6 depicts a user interface for predicting a waypoint stop in routeto a destination, rerouting the vehicle based on the waypoint stop, anddetermining a time of arrival to the destination, according toembodiments disclosed herein;

FIG. 7 depicts a flowchart for determining a time of arrival, based on apredicted waypoint stop, according to embodiments disclosed herein; and

FIG. 8 depicts a vehicle computing device that may provide routingand/or estimated time of arrival data for the vehicle, according toembodiments disclosed herein.

DETAILED DESCRIPTION

Embodiments disclosed herein include systems and methods for estimatingtime of arrival for vehicle navigation. Some embodiments are configuredto determine if a stop will likely be made during the trip. As anexample, the vehicle computing device may receive an indicationregarding the current vehicle fuel level and may determine the vehiclefuel consumption and whether the vehicle can reach the destinationwithout refueling. If not, the vehicle computing device may add apredetermined amount of time to the estimated time of arrival (ETA) toaccount for traveling to the waypoint and stopping to refuel. In thisexample, the additional time may be determined as a preset (or useridentified) amount of time, based on whether the vehicle is an internalcombustion engine (e.g., 10 minutes) or an electric engine (e.g., 4hours). Similarly, some embodiments may be configured to dynamicallycalculate the additional time, based on past user actions, preferredfueling stations along the route, etc.

While the vehicle computing device may adjust the ETA based on refuelingrequirements of the vehicle, other factors may cause an adjustment tothe ETA. As an example, if a user routinely stops at a particular pointof interest along the route, or if the user routinely stops after acertain amount of travel time, the vehicle computing device mayrecognize these stops and the additional time that the stops add to theETA. This additional time may be added to the ETA on future trips.

Accordingly, embodiments disclosed herein allow for greater accuracy indetermining time of arrival, distance, and other factors of a trip.These embodiments may additionally provide more accurate routing of thevehicle, based on the determined stops.

Referring now to the drawings, FIG. 1 depicts a vehicle interior,according to embodiments disclosed herein. As illustrated, a vehicle 102may include the vehicle interior with a console display 124 a and a dashdisplay 124 b (referred to independently and/or collectively herein as“display device 124”). The console display 124 a may be configured toprovide one or more user interfaces and may be configured as a touchscreen and/or include other features for receiving user input. The dashdisplay 124 b may similarly be configured to provide one or moreinterfaces, but often the data provided in the dash display 124 b is asubset of the data provided by the console display 124 a. Regardless, atleast a portion of the user interfaces depicted and described herein maybe provided on either or both the console display 124 a and the dashdisplay 124 b.

The vehicle 102 also includes a speedometer 152, a fuel gauge 154, andan odometer 156. The speedometer 152 may be configured to determine acurrent speed of the vehicle 102. Similarly, the fuel gauge 154 may becoupled to a fuel sensor that determines a current level of fuel in thevehicle 102. The odometer 156 may determine a distance that the vehicle102 has traveled over the life of the vehicle 102 and/or for apredetermined time period.

Also included in the vehicle 102 is a vehicle computing device 114. Thevehicle computing device 114 may be configured with a processor 132 anda memory component 134, which may store routing logic 144 a and traveltime logic 144 b. The routing logic 144 a and the travel time logic 144b may each include a plurality of different pieces of logic, each ofwhich may be embodied as a computer program, firmware, and/or hardware,as an example. The routing logic 144 a may be configured to cause thevehicle computing device 114 to determine navigational or routing datato the user. Specifically, the routing logic 144 a may be configured assoftware for a navigation system or otherwise facilitate communicationwith satellite or other remote computing device to determine a currentposition, as well as a route to a destination. Similarly, the traveltime logic 144 b may be configured to cause the vehicle computing device114 to determine a travel time for reaching the destination and predictwaypoints, which may add time to reach the destination. Additionalcomponents of the vehicle 102 are depicted in FIG. 8 and described inmore detail below.

It should be understood that while the vehicle computing device 114 mayprovide the functionality described herein, this is merely an example.In some embodiments, a remote computing device (such as the remotecomputing device 804 in FIG. 8) may be configured to determine vehicleposition, routing, estimated time of arrival, and/or other informationdescribed herein.

FIG. 2 depicts a user interface 230 for selecting a destination that maybe provided by a vehicle computing device 114, according to embodimentsdisclosed herein. As illustrated, the user interface 230 may be providedto the user (driver and/or passenger) of the vehicle 102 to determinerouting and/or an estimated time of arrival for reaching a destination.As discussed above, a determination may be made regarding the currentposition of the vehicle 102. Additionally, the user interface 230 mayprovide user options 232 a, 232 b, 232 c, and 232 d for determining adestination to which the user will be traveling.

It should be understood that while the user may manually enter thedesired destination, as illustrated in FIG. 2, this is merely anexample. In some embodiments, the vehicle computing device 114 maydetermine the destination based on past user actions and/or otherinformation. Regardless of the manner in which the vehicle computingdevice 114 receives the destination, this information may be utilizedfor determining a route and/or a time of arrival to the destination, asdescribed below.

FIG. 3 depicts a user interface 330 for viewing a route that may beplanned by a vehicle computing device 114, according to embodimentsdisclosed herein. Based on the current position of the vehicle 102 andthe destination, a route 336 may be determined for reaching thedestination. This route 336 may be illustrated in the user interface330, which shows a vehicle indicator 332 and a destination indicator334. Also included in the user interface 330 is distance data 338 a,current time data 338 b, time to destination data 338 c, and estimatedtime of arrival data 338 d. The distance data 338 a provides the lineardistance from the current vehicle location to the destination.Specifically, the distance data 338 a may be calculated by determining aroute from the current vehicle location to the destination anddetermining distance the vehicle 102 will travel along the route toreach the destination.

The current time data 338 b may provide the current time, which may bereceived from an internal clock and/or from a remote computing device.The time to destination data 338 c may identify a predicted time forreaching the destination, based on the distance data 338 a, as well as aspeed that the vehicle 102 may travel along the route to reach thedestination. In some embodiments, the vehicle computing device 114 mayreceive speed limit data for each of the roads that the vehicle 102 willtraverse to reach the destination and utilize this data to determine thetime to destination data 338 c. In some embodiments however, the time todestination data 338 c may be determined based on a predetermineddefault speed of the vehicle 102 (e.g., always use 55 miles per hour onhighways and always use 35 miles per hour on non-highway roads).Similarly, the vehicle computing device 114 may utilize past useractions on those roads or other roads to determine the speed that thevehicle 102 will take to reach the destination. Regardless, with thespeed data, the time to destination data 338 c may be calculated.Similarly, the estimated time of arrival data 338 d may be calculatedfrom the time to destination data 338 c and the current time data 338 b.The estimated time of arrival data 338 d may provide the estimated timeof arrival for reaching the destination, based on the current time data338 b and the time to destination data 338 c.

Also included in the user interface 330 are an options button 340, aschedule stop button 342, and a stop now button 344. Specifically, theoptions button 340 may provide options for more accurate routing and/ortravel time information, as described below. The schedule stop button342 may allow the user to provide a scheduling user input to manuallyschedule a stop for a future time. As an example, if the user (passengeror driver) knows that there will be a desire to refuel the vehicle 102at a certain time or certain fuel level, the user may select theschedule stop button 342 to enter the nature of the stop. In thisexample, the stop will be a vehicle-based waypoint in the form ofrefueling. Accordingly, the user may additionally enter the desired timefor stopping, the desired fuel level to trigger the waypoint, thedesired destination of the waypoint, the desired fuel provider, and/orother information for the scheduling the waypoint stop. As described inmore detail below, the vehicle computing device 114 may revise the route336, the travel time, and/or the estimated time of arrival, based on aprediction of the time and/or distance to reach and stop at thewaypoint.

Similarly, the user may provide an impromptu user input of the stop nowbutton 344 to immediately route the vehicle 102 to the desired stoppingpoint. As an example, if the vehicle 102 is low on fuel or if a restroomstop must be made immediately, the user may select the stop now button344. In response, the vehicle computing device 114 may provide optionsfor the type of stop, such as fuel stations and/or restrooms in theimmediate vicinity.

FIG. 4 depicts a user interface 430 for providing one or more optionsrelated to calculating a time of arrival to a destination, according toembodiments disclosed herein. In response to selection of the optionsbutton 340 from FIG. 3, the user interface 430 may be provided and mayinclude a calculate option 432 a, a favorite option 432 b, a fastestoption 432 c, an additional time option 432 d, and a present time option432 e. By activating the calculate option 432 a, the vehicle computingdevice 114 may calculate a time for reaching the waypoint and then thedestination and include this calculation into the time to destinationdata 338 c and/or the estimated time of arrival data 338 d (FIG. 3). Asan example, if a waypoint is determined to be a fuel stop, the vehiclecomputing device 114 may determine the exact fuel station where thevehicle 102 will stop. The vehicle computing device 114 may additionallydetermine the distance to the waypoint, the distance from the waypointto the destination, and calculate a travel time based on that distance.

Similarly, the favorite option 432 b may be selected to store and recallfavorite waypoints of a user. Specifically, if a user always stops at aparticular fuel brand, restaurant, highway exit, or other waypoint, thevehicle computing device 114 may store this information, such thatrecommendations and/or automatic routing and travel time may beprovided. The fastest option 432 c may be selected such that the vehiclecomputing device 114 determines a location and a predicted time forstopping at a plurality of candidate waypoints. The vehicle computingdevice 114 may then select the one or more waypoints which will add theleast amount of time to the trip.

Also included are the additional time option 432 d and the present timeoption 432 e. Selection of the calculate additional time option 432 dcauses the vehicle computing device 114 to calculate the time thatstopping at the waypoint will add to the travel time. As discussedabove, the added time for traveling to the waypoint and from thewaypoint to the destination may be calculated based on distance andspeed. However, the additional time option 432 d may also calculate thetime that the stop itself will take. Accordingly, in response toselection of the additional time option 432 d, the vehicle computingdevice 114 may predict an estimated time for the stop and add thatadditional time to the time to destination data 338 c. The vehiclecomputing device 114 may predict the additional time, based on the typeof waypoint stop, past user actions, a determined traffic flow at thewaypoint, and/or from other data. As an example, if the vehicle 102 hasan internal combustion engine, and the fuel tank of the vehicle 102 isempty, the vehicle computing device 114 may determine a normal amount oftime for filling the tank. If the user generally refills the fuel tankonly half full, the vehicle computing device 114 may account for thatamount of time. Additionally, if the user always takes between 15 and 20minutes at this waypoint, that information may be utilized for thiscalculation.

Similarly, the preset time option 432 may be selected to always utilizea preset time for determining waypoint stopping times. Specifically, ifthe preset time option 432 is selected and the waypoint is a gasolinestop, the vehicle computing device 114 may always add 6 minutes to thetime to destination data 338 c. If the waypoint is an electric vehiclerefueling, the vehicle computing device 114 may always add 4.2 hours forrecharging. Other stops may be automatically preset and in someembodiments, all waypoints may have a single preset time, regardless ofthe type of waypoint.

FIG. 5 depicts a user interface 530 for calculating a time of arrival toa destination, while factoring in one or more waypoint stops, accordingto embodiments disclosed herein. As illustrated in the user interface530, a route 532 may be provided from the current location to thedestination. Additionally, the user interface 530 includes destinationdata 534, which includes distance data 534 a, current time data 534 b,stop data 534 c, time for stop data 534 d, time to destination data 534e, and ETA to destination data 534 f. Also included are an optionsbutton 536, a schedule stop button 538, and a stop now button 540.

Specifically, after a destination is determined, the vehicle computingdevice 114 may determine a waypoint that will be reached along theroute. The waypoint may include vehicle-based waypoints and/oruser-based waypoints. The vehicle-based waypoints may include anywaypoint that is included to address some part of the vehicle 102.Examples include waypoints for predetermined fuel level (e.g., if thetank reaches an empty threshold), a predetermined maintenance level(e.g., if the oil alarm and/or maintenance alarm are activated), anexpected fuel level (e.g., if the vehicle 102 will reach the emptythreshold after a predicted amount of time based on current orhistorical fuel consumption), an expected maintenance level, a vehiclewash, a weather-related stop, etc. User-based waypoints include thosethat relate to the user (driver and/or passenger). Examples ofuser-based waypoints include waypoints for a restaurant stop, a restroomstop, an entertainment establishment stop, a hospital stop, a siteseeing establishment stop, etc. User-based waypoints may also bedetermined in a number of ways, including utilizing previously storeduser actions for predicting a waypoint along the route.

Regardless of the type of waypoint, the vehicle computing device 114 maydetermine the waypoint from any of a number of different mechanisms. Asan example, the user may select the schedule stop button 538 to schedulea future waypoint along the route. In response to selection of the stopnow button 540, the user may initiate location and routing of animpromptu waypoint in the immediate vicinity of the vehicle 102.Similarly, the vehicle computing device 114 may be configured to inferwaypoints based an action of the vehicle 102 (such as exiting thehighway unexpectedly), based on past user actions and/or based on storedsettings. As an example, the vehicle computing device 114 may determinethat vehicle 102 will not be able to reach the destination withoutrefueling. Accordingly, the vehicle computing device 114 mayautomatically determine (such as from a user setting, a past useraction, or other determination) a refueling station and add thisvehicle-based waypoint to the route. In some embodiments, the vehiclecomputing device 114 may prompt the user for a desired refuelingstation.

Similarly, the vehicle computing device 114 may determine that at leastone of the users will likely need a restroom break before reaching thedestination. Accordingly, the vehicle computing device 114 may identifyan approximate time that the restroom break will be needed and locate anappropriate establishment for this user-based waypoint. Similarly, ifthe vehicle 102 will not reach the destination before an eating time, arestaurant may be selected and/or included as a waypoint along theroute. One or more such waypoints may be added to the route. If the userselects the stop now button 344 for a restroom break that is differentthan then inferred restroom break, the vehicle computing device 114 mayremove the inferred waypoint stop, reroute and/or estimate ETA with theimpromptu waypoint stop, and store the user input and waypoint stop forfuture waypoint inferences.

Once the one or more waypoints are determined, the vehicle computingdevice 114 may additionally determine whether the vehicle 102 will needto be rerouted from the route 336 (FIG. 3). If not, the route 336 andthus the distance data 338 a may remain the same (as in route 532) andthe waypoint stop may be accounted in the time to destination data 534 eand the ETA to destination data 534 f. If the vehicle 102 will bererouted based on the waypoint, the rerouting may be performed, newdistance data may be calculated, and the destination data and ETA datamay be updated, as is described with reference to FIG. 6.

FIG. 6 depicts a user interface 630 for predicting a waypoint stop inroute to a destination, rerouting the vehicle 102 based on the waypointstop, and determining a time of arrival to the destination, according toembodiments disclosed herein. As illustrated, the user interface 630includes a revised route 632 a that accounts for a determined waypoint.Specifically, a determination was made that the vehicle 102 would make afuel stop at a fueling station. Upon determining the specific fuelingstation 632 b, the vehicle computing device 114 determines whether theroute needs to be altered to account for the waypoint. In the embodimentof FIG. 6, it is determined that the most efficient (or desired) routeis to proceed according to the revised route 632 a, which is differentthan the original route. Additionally, distance data 634 a is changed toaccount for the waypoint.

Also included in the user interface 630 are stops data 634 b, addeddistance data 634 c, added time data 634 d, time to destination data 634e, and ETA to destination data 634 f. As illustrated, the time todestination data 634 e and the ETA to destination data 634 f are updatedaccording to the added distance data 634 c. ETA to stop data 634 g isalso provided to indicate when the vehicle 102 will reach the specificfueling station 632 b.

FIG. 7 depicts a flowchart for determining a time of arrival, based on apredicted waypoint stop, according to embodiments disclosed herein. Asillustrated in block 750, a route for a vehicle may be determined toreach a destination from a current location. In block 752, an estimatedtime for reaching the destination from the current location may also bedetermined. In block 754, a current range of the vehicle may bedetermined, where this determination is based on current fuel level andvehicle fuel efficiency. In block 756, a determination, based on thecurrent range, is made regarding whether the vehicle can reach thedestination without refueling. In block 758, in response to determiningthat the vehicle cannot reach the destination without refueling, theestimated time for reaching the destination may be revised to include awaypoint to refuel. In block 760, the estimated time for reaching thedestination may be provided for display to a user.

FIG. 8 depicts a vehicle computing device 114 that may provide routingand/or estimated time of arrival data for the vehicle, according toembodiments disclosed herein. The vehicle 102 is depicted in FIG. 8 asan automobile but may be any passenger or non-passenger vehicle such as,for example, a terrestrial, aquatic, and/or airborne vehicle may beincluded. The vehicle 102 may be coupled to a remote computing device804 and/or a user computing device 806 for receiving content and/orother data via a network 800. The network may include a wide areanetwork, local area network, and/or other wired or wireless network forcommunicating data, as described herein.

Also illustrated is the vehicle computing device 114, which includes theprocessor 132, input/output hardware 808, the network interface hardware850, a data storage component 836 (which stores mapping data 838 a,travel time data 838 b, and/or other data), and the memory component134. The memory component 134 may be configured as volatile and/ornonvolatile memory and as such, may include random access memory(including SRAM, DRAM, and/or other types of RAM), flash memory, securedigital (SD) memory, registers, compact discs (CD), digital versatilediscs (DVD), and/or other types of non-transitory computer-readablemediums. Depending on the particular embodiment, these non-transitorycomputer-readable mediums may reside within the vehicle computing device114 and/or external to the vehicle computing device 114.

The memory component 134 may store operating logic 842, the routinglogic 144 a and the travel time logic 144 b. The routing logic 144 a andthe travel time logic 144 b may each include a plurality of differentpieces of logic, each of which may be embodied as a computer program,firmware, and/or hardware, as an example. A local interface 834 is alsoincluded in FIG. 8 and may be implemented as a bus or othercommunication interface to facilitate communication among the componentsof the vehicle computing device 114.

The processor 132 may include any processing component operable toreceive and execute instructions (such as from a data storage component836 and/or the memory component 134). As described above, theinput/output hardware 808 may include and/or be configured to interfacewith the components of FIG. 8. As an example, the input/output hardware808 may include microphones, speakers, the display device 124, the fuelgauge 154, the speedometer 152, the odometer 156 (FIG. 1), and/or otherhardware in the vehicle 102

The network interface hardware 850 may include and/or be configured forcommunicating with any wired or wireless networking hardware, includingan antenna, a modem, a LAN port, wireless fidelity (Wi-Fi) card, WiMaxcard, mobile communications hardware, and/or other hardware forcommunicating with other networks and/or devices. From this connection,communication may be facilitated between the vehicle computing device114 and other computing devices.

The operating logic 842 may include an operating system and/or othersoftware for managing components of the vehicle computing device 114.Similarly, as discussed above, the routing logic 144 a may reside in thememory component 134 and may be configured to cause the processor 132 todetermine location and/or routing of the vehicle. Similarly, the traveltime logic 144 b may be utilized to determine the waypoints andadditional times of travel related to the waypoints.

It should be understood that while the components in FIG. 8 areillustrated as residing within the vehicle computing device 114, this ismerely an example. In some embodiments, one or more of the componentsmay reside external to the vehicle computing device 114. It should alsobe understood that, while the vehicle computing device 114 isillustrated as a single device, this is also merely an example. In someembodiments, the routing logic 144 a and the travel time logic 144 b mayreside on different computing devices. As an example, one or more of thefunctionalities and/or components described herein may be provided by aremote computing device 804 and/or user computing device 806, which maybe coupled to the vehicle 102 via a network 800, which may be embodiedas a wide area network and/or local area network.

Additionally, while the vehicle computing device 114 is illustrated withthe routing logic 144 a and the travel time logic 144 b as separatelogical components, this is also an example. In some embodiments, asingle piece of logic may cause the vehicle computing device 114 toprovide the described functionality.

As illustrated above, various embodiments for estimating time of arrivalfor vehicle navigation are disclosed. These embodiments allow fordynamic alteration of travel times and routes to a destination.Embodiments disclosed herein also enable more accurate travel times andestimated times of arrival for a vehicle to a destination.

While particular embodiments and aspects of the present disclosure havebeen illustrated and described herein, various other changes andmodifications can be made without departing from the spirit and scope ofthe disclosure. Moreover, although various aspects have been describedherein, such aspects need not be utilized in combination. Accordingly,it is therefore intended that the appended claims cover all such changesand modifications that are within the scope of the embodiments shown anddescribed herein. It should now be understood that embodiments disclosedherein are merely exemplary and are not intended to limit the scope ofthis disclosure.

What is claimed is:
 1. A method for estimating time of arrival forvehicle navigation comprising: determining, by a computing device, aroute for a vehicle to reach a destination from a current location;determining, by the computing device, an estimated time for reaching thedestination from the current location; determining, by the computingdevice, a current range of the vehicle, based on a current fuel leveland a vehicle fuel efficiency; determining, by the computing device,based on the current range, and after the vehicle has traveled a portionof the planned route, whether the vehicle can reach the destinationwithout refueling; in response to determining that the vehicle cannotreach the destination without refueling, revising, by the computingdevice, the estimated time for reaching the destination to include awaypoint to refuel, wherein revising the estimated time includescalculating a time that the vehicle will be stopped at the waypoint; andproviding, by the computing device, the estimated time for reaching thedestination for display to a user.
 2. The method of claim 1, furthercomprising predicting a user-based waypoint.
 3. The method of claim 2,wherein the user-based waypoint comprises at least one of the following:a restroom stop, a restaurant stop, and a site seeing establishmentstop.
 4. The method of claim 2, wherein the user-based waypoint isdetermined from at least one of the following: a scheduling user inputto schedule the waypoint for a future time, an impromptu user input toidentify a stop at a present time, a determination based on previoususer actions, and an action of the vehicle.
 5. The method of claim 4,further comprising storing user actions associated with the waypoint andwherein determining the user-based waypoint from previous user actionscomprises utilizing previously stored user actions for predicting thewaypoint along the route.
 6. The method of claim 4, wherein determiningthe user-based waypoint from the action of the vehicle comprisesdetermining that the vehicle is taking an impromptu waypoint withoutprevious indication, determining a nature of the waypoint, and alteringthe estimated time for reaching the destination.
 7. The method of claim4, further comprising, in response to determining that the vehiclecannot reach the destination without refueling, rerouting the vehicle toaccount for the waypoint.
 8. A system for estimating time of arrival forvehicle navigation comprising: an odometer for determining distancestraveled by the vehicle; a fuel gauge for determining a current fuellevel of the vehicle; and a computing device, wherein the computingdevice stores logic that, when executed by a processor, causes thecomputing device to perform at least the following: determine a distancefor reaching a destination from a current location; determine a currentrange of the vehicle, based on the current fuel level and a vehicle fuelefficiency; determine, after the vehicle has traveled a portion of theplanned route and based on the current range, whether the vehicle canreach the destination without refueling; in response to determining thatthe vehicle cannot reach the destination without refueling, determine anestimated time for reaching the destination, wherein the estimated timefor reaching the destination includes travel time to waypoint to refueland a predicted time that the vehicle will be stopped at the waypoint;and provide the estimated time for reaching the destination for displayto a user.
 9. The system of claim 8, wherein the logic further causesthe computing device to predict at least one of the following: auser-based waypoint and a vehicle-based waypoint.
 10. The system ofclaim 9, wherein the user-based waypoint comprises at least one of thefollowing: a restroom stop, a restaurant stop, and a site seeingestablishment stop.
 11. The system of claim 9, wherein the user-basedwaypoint is determined from at least one of the following: a schedulinguser input to schedule the waypoint for a future time, an impromptu userinput to identify a stop at a present time, a determination based onprevious user actions, and an action of the vehicle.
 12. The system ofclaim 11, wherein the logic further causes the computing device to storea user action associated with the waypoint and wherein determining theuser-based waypoint from previous user actions comprises utilizingpreviously stored user actions for predicting the waypoint along a routeof the vehicle.
 13. The system of claim 11, wherein determining theuser-based waypoint from the action of the vehicle comprises determiningthat the vehicle is taking an impromptu waypoint without previousindication, determining a nature of the waypoint, and altering theestimated time for reaching the destination.
 14. The system of claim 9,wherein, in response to determining that the vehicle cannot reach thedestination without refueling, the logic further causes the computingdevice to reroute the vehicle to account for the waypoint.
 15. A systemfor estimating time of arrival for vehicle navigation comprising: avehicle; and a computing device, wherein the computing device storeslogic that, when executed by a processor, causes the computing device toperform at least the following: determine an estimated time for reachinga destination from a current location; predict, after the vehicle hastraveled a portion of a route to the destination, whether a waypointwill be taken before reaching the destination; in response todetermining that the vehicle will take the waypoint before reaching thedestination, revise the estimated time for reaching the destination toinclude the wherein revising the estimated time includes calculating atime that the vehicle will be stopped at the waypoint; and provide theestimated time for reaching the destination for display to a user. 16.The system of claim 15, wherein determining whether the waypoint will betaken before reaching the destination comprises at least one of thefollowing: predicting a user-based waypoint and predicting avehicle-based waypoint.
 17. The system of claim 16, wherein theuser-based waypoint comprises at least one of the following: a restroomstop, a restaurant stop, and a site seeing establishment stop andwherein the vehicle-based waypoint comprises at least one of thefollowing: refueling, vehicle maintenance, and a weather-related stop.18. The system of claim 16, wherein the user-based waypoint isdetermined from at least one of the following: a scheduling user inputto schedule the waypoint for a future time, an impromptu user input toidentify a stop at a present time, a determination based on previoususer actions, and an action of the vehicle.
 19. The system of claim 18,wherein the logic further causes the computing device to store a useraction associated with the waypoint and wherein determining theuser-based waypoint from previous user actions comprises utilizingpreviously stored user actions for predicting the waypoint along a routeof the vehicle.
 20. The system of claim 18, wherein determining theuser-based waypoint from the action of the vehicle comprises determiningthat the vehicle is taking an impromptu waypoint without previousindication, determining a nature of the waypoint, and altering theestimated time for reaching the destination.